home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941031-19941221
/
000069_news@columbia.edu_Mon Nov 7 22:02:41 1994.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA05539
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 7 Nov 1994 17:02:46 -0500
Received: by apakabar.cc.columbia.edu id AA12045
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 7 Nov 1994 17:02:44 -0500
Path: news.columbia.edu!usenet
From: fdc@fdc.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Receiving files "automatically"
Date: 7 Nov 1994 22:02:41 GMT
Organization: Columbia University
Lines: 63
Message-Id: <39m861$bob@apakabar.cc.columbia.edu>
References: <DRW.94Nov7142624@runge.mit.edu>
Nntp-Posting-Host: fdc.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <DRW.94Nov7142624@runge.mit.edu> drw@runge.mit.edu (Dale R.
Worley) writes:
> In article <CyLouB.6Lu@ritz.mordor.com> kudut@ritz.mordor.com (Ken Udut)
> writes:
> >And why is it that Kermit comes with almost no documentation?
>
> It comes with a *lot* of documentation. The KERMIT.BWR and KERMIT.UPD
> file are both sets of documentation. If you issue a HELP at the Kermit
> prompt, you get more information. While you are typing in a comment,
> but you are not sure what to type in next, press a ?, and you will
> magically get help for that command.
>
> Well, it comes with a lot of documentation files, but they're
> hellishly organized. The DIAL command, the second most important
> feature (the first is terminal emulation), isn't in KERMIT.HLP, the
> obvious documentation file, but is banished to the "Release notes"
> file for some incomprehensible reason. Since one expects DIAL to have
> been is version 1.0000, one does not naturally think of looking in the
> release notes for it.
>
But if one looks up the DIAL command in KERMIT.HLP, one sees "See
KERMIT.UPD". So it should not be that hard to figure out.
> And what is "KERMIT.BWR"? Last I heard, "BWR" stands for Boiling
> Water Reactor. Put the documentation in one place, fer crying out
> loud, don't scatter it among a half-dozen files.
>
For the historical-minded, Kermit was first developed in the early 80s when
DEC was in its heyday, and every university had a DEC-10 or DEC-20 or a
VAX. DEC software releases always included a "beware file", with file
type .BWR. The idea was to get peoples' attention when something went
wrong, and everybody knew to "look in the BWR file" before reporting bugs,
etc. Those days are over, of course, and perhaps it would it be more
intuitive (at least to newsgroup readers) to call them .FAQ files, but
then we'd have to recast them all in question-and-answer form, like in
Jeopardy, to avoid the inevitable rash of complaints. But, given limited
resources and time, and an infinite amount of demand, this settles to a
rather low rung on the priority ladder.
The simple fact is that Kermit, like a great deal of other software, comes
with a manual, and then some other files to supplement the manual, either
in the form of updates, or technical hints and tips. Unlike a lot of this
other software, however, it also comes with a brief help file listing all
the commands. I don't think this is something to complain about.
> And if you make the mistake of starting Kermit when the current
> directory is not the installation directory, then Kermit can't find
> its initization files, and voila! DIAL simply disappears. (I don't
> know about the PC world, but as a general thing, Unix software is
> bright enough to be able to find its initialization files on its own.)
>
Like most other DOS programs, Kermit needs to know where its ancilliary
files are so it can behave in a consistent way no matter what directory
you start it from. What would you have it do -- a "find file" over all of
your disks? The installation instructions are excruciatingly simple:
Make a directory for the Kermit files, and then add that directory to your
DOS PATH. See the READ.ME file in the MS-DOS Kermit 3.14 ZIP file.
The preceeding, of course, is for the benefit of those who want to use the
software but don't want to consult the manual. We don't get a lot of
complaints from Kermit users who *do* have the manual.
- Frank